The are some errors in the macOS 13.3 SDK from current Xcode 14.3 Beta2 All CGDisplayStream... Calls are now flaged like this CG_EXTERN CGError CGDisplayStreamStop(CGDisplayStreamRef cg_nullable displayStream)   CG_AVAILABLE_BUT_DEPRECATED(13.0, 14.0, "Please use ScreenCaptureKit API's stopCaptureWithCompletionHandler: to stop a stream instead"); in macOS 13.0 SDK this call was flagged only flagged with CG_EXTERN CGError CGDisplayStreamStop(CGDisplayStreamRef cg_nullable displayStream)    CG_AVAILABLE_STARTING(10.8); The Error here is the in MacOS 13.3 SDK it should be something like CG_AVAILABLE_BUT_DEPRECATED(10.8, 14.0, "Please use ScreenCaptureKit API's ...

I developed a Audio Server PlugIn, based on the SimpleAudioDriver sample. It works fine on my development machine. Now I want to distribute it with the rest of our app. For that I set up the CODE_SIGN_IDENTITY parameter for our Developer ID Application certificate. Build and signment works fine. Now I put everything together in an installer package and try to install it on different machines, but the driver was rejected and did not work. I also tried to notarise the package but did get an error saying that my code isn't signed at all. And indeed the _CodeSignature/CodeResources file inside my driver did not have an entry for the binary. Any ideas what I made wrong or what I did miss?

macOS flag is: -mmacosx-version-min=xx.yy iphoneos flag is: -mios-version-min=xx.yy iphonesimulator flag is: -mios-simulator-version-min=xx.yy but for xros things are going crazy .... xros flag -mtargetos=xrosxx.yy works well xrsimulator flag -mtargetos=xrosxx.yy or -mtargetos=xrsimulatorxx.yy are not working Does anyone no which is the right flag

We have a huge app with many frameworks. I want to use address sanitizer with it. After enable it in Xcode and recompile the app does not start. dyld[73936]: dyld cache '(null)' not loaded: syscall to map cache into shared region failed dyld[73936]: Library not loaded: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation   Referenced from: <926AEF5E-4934-3EA0-BC60-64CC0A28EC0C> /Users/schmitt/Library/Developer/Xcode/DerivedData/TeamViewerWorkspace-bzqkzpkzdmerjreghjwkjpbhtmua/Build/Products/Debug/TeamViewer.app/Contents/MacOS/TeamViewer   Reason: tried: '/Users/schmitt/Library/Developer/Xcode/DerivedData/TeamViewerWorkspace-bzqkzpkzdmerjreghjwkjpbhtmua/Build/Products/Debug/Foundation.framework/Versions/C/Foundation' (no such file), '/Users/schmitt/Library/Developer/Xcode/DerivedData/TeamViewerWorkspace-bzqkzpkzdmerjreghjwkjpbhtmua/Build/Products/Debug/PackageFrameworks/Foundation.framework/Versions/C/Foundation' (no such file), '/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation' (no such file), '/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation' (no such file, no dyld cache), '/Library/Frameworks/Foundation.framework/Versions/C/Foundation' (no such file) It looks like Foundation.framework is no longer found. When I try the same thing with a new app from the macOS app template and link it to our frameworks, the app launches normally. I have tried playing with the deployment target, but have no luck getting any clues as to what is going wrong